Cloud computing environment with split connectivity and application interfaces that enable support of separate cloud services

ABSTRACT

A cloud service provider network may receive, from a cloud subscriber device, a request to access an application, wherein the cloud service provider network includes a split interface associated with the cloud subscriber device. The cloud service provider network may provide, to the cloud operator device, the request to access the application, wherein the cloud operator device stores the application. The cloud service provider network may receive, from the cloud operator device, the application, based on the request to access the application. The cloud service provider network may provide the application to the cloud subscriber device via the application interface of the split interface, wherein the connectivity interface connects the cloud subscriber device and the cloud operator device so that the application is provided to the cloud subscriber device via the application interface.

BACKGROUND

In recent years, types of user devices that utilize cloud-based serviceshave grown rapidly with little standardization. Users of the userdevices prefer services that are on-demand, scalable, highly available,secure, utilize usage-based billing, and/or the like. In order to meetthese preferences, cloud connectivity providers and cloud applicationproviders need to be able to quickly create the services and utilizeresources effectively.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1O are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented. The environment includescompute, storage and networking resources.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process for supporting separatecloud services with a cloud computing environment that includes splitconnectivity and application interfaces.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Cloud connectivity providers and cloud application providers are oftenunable to efficiently provide services to users due to current cloudarchitectural constraints. This results in waste of computing resources(e.g., processing resources, memory resources, communication resources,and/or the like), networking resources, and/or the like in providingcloud services to user devices associated with the users.

Some implementations described herein provide a cloud computing,storage, and networking environment (referred to herein as “cloudcomputing environment”) with split connectivity and applicationinterfaces that enable support of separate cloud services. For example,the cloud computing environment may include a cloud service providernetwork that may receive, from a cloud subscriber device, a request toaccess an application. The cloud service provider network may include asplit interface associated with the cloud subscriber device. The splitinterface may include a connectivity interface associated with aconnectivity operator device, and an application interface associatedwith a cloud operator device. The cloud service provider network mayprovide, to the cloud operator device, the request to access theapplication, wherein the cloud operator device stores the application,and may receive, from the cloud operator device, the application basedon the request to access the application. The cloud service providernetwork may provide the application to the cloud subscriber device viathe application interface of the split interface. The connectivityinterface connects the cloud subscriber device and the cloud operatordevice so that the application is provided to the cloud subscriberdevice via the application interface.

In this way, the cloud computing environment with the split connectivityand application interfaces enables cloud services to be more efficientlyprovided to users. Thus, the cloud computing environment conservescomputing resources (e.g., processing resources, memory resources,communication resources, and/or the like), networking resources, and/orthe like that would otherwise be wasted attempting to provide the cloudservices without the split connectivity and application interfaces.

FIGS. 1A-1O are diagrams of one or more example implementations 100described herein. As shown in FIG. 1A, a cloud subscriber 105 may beassociated with a cloud service provider network 110. Cloud serviceprovider network 110 may include a cloud computing environment withcomputing resources that perform functionality associated withconnectivity operators 115-A and 115-B (e.g., also referred to asconnectivity operator 115), cloud operators 120-A and 120-B (e.g., alsoreferred to as cloud operator 120), and/or the like. Cloud serviceprovider network 110 may provide cloud services to cloud subscribers105. The cloud services may include computing resources, storageresources, applications, connectivity among the aforementioned, and/orthe like, that may be accessed by cloud subscribers 105 from one or morelocations. Cloud subscriber 105 may include an end-user that maintains abusiness relationship with and utilizes services from cloud serviceprovider network 110. Connectivity operator 115 may provide connectivityservices between cloud operators 120, connectivity operators 115, cloudsubscribers 105, and/or the like. Cloud operator 120 may make cloudapplications available to cloud subscribers 105. A cloud serviceprovider (e.g., associated with cloud service provider network 110) maybe responsible for creation, delivery, and billing of cloud services;negotiating relationships among cloud subscribers 105, connectivityoperators 115, and cloud operators 120; and providing a single point ofcontact for cloud subscribers 105.

In some implementations, for a particular cloud service, cloudsubscriber 105 may contract with cloud service provider network 110 tobe responsible for delivering the particular cloud service at locationsassociated with cloud subscriber 105. Cloud service provider network110, in turn, may select and contract with various connectivityoperators 115 and cloud operators 120 to deliver the particular cloudservice to the locations. Cloud service provider network 110 may ensurethat the particular cloud service purchased by cloud subscriber 105 isdelivered. Various types of entities may act as a cloud serviceprovider, such as a system integrator, a mobile operator, an Internetservice provider (ISP), a cloud operator, a cloud subscriber, and/or thelike.

In some implementations, the cloud services may include connectivity andapplication functionalities with operational flexibility in serviceorder, provisioning, monitoring, billing, and/or the like. In cloudservices, networking, compute, storage, and applications may be treatedtogether as a single service provided to cloud subscriber 105.Capabilities provided by virtual network functions (VNFs) and networkfunction virtualization infrastructure (NFVI) may be utilized by cloudservices. For operational flexibility, virtualized components may beutilized by cloud subscriber 105. For example, a cloud security servicevia a virtual firewall can be provided at subscriber premises, in a datacenter in a core network, or anywhere in between, based on a subscriberrequest.

In some implementations, a cloud service may combine connectivity andapplications with compute, storage, and networking resources; mayinclude virtualized components (e.g., VNFs) and non-virtualizedcomponents (e.g. physical network functions (PNFs)) that may or may notbe exposed to cloud subscriber 105; may include network functions withonly non-virtualized components or both virtualized components andnon-virtualized components that may not be fully exposed to cloudsubscriber 105; may include applications built with virtualizedcomponents that may not be fully exposed to cloud subscriber 105; mayinclude connections provided by one or more cloud operators 120 and/ornetwork operators (e.g., connectivity operators 115); may supporton-demand service configurations by cloud subscribers 105 and locationsof service functionality; may support service monitoring andusage-tracking by cloud subscribers 105; may support self-service bycloud subscribers 105 and collaboration among connectivity operators 115and cloud operators 120 in providing resources; may support scalabilityof resources on-demand; may support various high-availability optionsfrom a physical layer to an application layer; may support usage-basedbilling; and/or the like.

In some implementations, an interface may be provided between cloudsubscriber 105 and cloud service provider network 110 and may bereferred to as a cloud subscriber interface. The cloud subscriberinterface may enable cloud subscriber 105 to connect to and operate overcloud platforms, connect and execute applications provided by cloudservice provider network 110, and/or the like. An interface may beprovided between cloud subscriber 105 and an application, between cloudapplications, between cloud operators 120, and/or the like. A connectionmay be provided between cloud subscriber 105 and an application, betweenand/or among cloud subscribers 105, between and/or among cloudapplications, and/or the like.

Cloud subscriber 105 may interface with cloud service provider network110 via a network (e.g., the Internet) and the cloud subscriberinterface. The cloud subscriber interface may include a connectivityinterface associated with a connectivity operator device (e.g.,connectivity operator 115) and an application interface associated witha cloud operator device (e.g., cloud operator 120). For example, asshown to the left in FIG. 1B, the cloud subscriber interface may includea connectivity interface that includes a cloud connectivityuser-to-network interface (UNI) 125 and an application interface thatincludes cloud application UNIs 130. In some implementations, cloudsubscriber 105 may access cloud service provider network 110 via aprivate network and the connectivity interface. Additionally, oralternatively, cloud subscriber 105 may access cloud service providernetwork 110 via a public network and the connectivity interface. In someimplementations, connectivity operator 115 may connect with cloudoperator 120 and may enable connectivity of cloud subscriber device 105to cloud operator device 120.

In some implementations, cloud service provider network 110 may includea split interface associated with cloud subscriber 105. For example, asshown in the middle of FIG. 1B, the cloud subscriber interface may besplit between cloud connectivity UNI 125 and cloud application UNI 130.In this way, the cloud subscriber interface enables separatecapabilities (e.g., connectivity and applications) to be supported byseparate cloud provider entities (e.g., connectivity operators 115 andcloud operators 120), and allows cloud application UNIs 130 to bedeployed at network edge devices as well as in internal network devices.For example, a connectivity operator 115 may provide connectivityservices through cloud connectivity UNI 125, and an application maytunnel through to a cloud operator 120 that provides the application.Another example may include function chaining, where functions may bedistributed across multiple cloud operators 120 and connected to eachother through cloud application UNIs 130 (e.g., a VNF in a first carriercore network that connects to a VNF in a second carrier core network,that may also connect to a VNF in an enterprise network serviced by thefirst or second carrier core networks). The cloud subscriber interfacealso enables providing cloud connectivity UNI 125 at network gateways,while placing cloud application UNI 130 at internal network nodes orvirtualized nodes.

In some implementations, cloud service provider network 110 may receive,from cloud subscriber 105, a request to access an application (e.g.,packets requesting access to the application), may route the request toaccess the application to a cloud operator device (e.g., cloud operator120) that stores the application, and may receive the application (e.g.,application packet data units (PDUs)) from the cloud operator devicebased on the request. In this case, cloud service provider network 110may provide the application to cloud subscriber 105 via the applicationinterface of the split interface, and the connectivity interface mayconnect cloud subscriber 105 and cloud operator 120 so that theapplication is provided to cloud subscriber 105 via the applicationinterface.

As shown to the right in FIG. 1B, the cloud subscriber interface mayinclude only cloud connectivity UNI 125 and may omit cloud applicationUNI 130 when only connectivity services are offered at the cloudsubscriber interface. As shown to the left in FIG. 1C, the cloudsubscriber interface may include cloud connectivity UNI 125, and cloudapplication UNI 130 may be located both within cloud subscriber 105 andwithin cloud service provider network 110. Cloud connectivity UNI 125 ofthe cloud subscriber interface may be provided at a location wherephysical connectivity occurs between cloud subscriber 105 and cloudservice provider network 110. Cloud application UNI 130 may be providedbetween cloud subscriber 105 applications and cloud service providernetwork 110 applications.

The cloud subscriber interface may demarcate domains managed by cloudservice provider network 110 and domains managed by cloud subscriber105. The cloud subscriber interface may be implemented over abi-directional link that provides various traffic, control plane, andmanagement capabilities required by cloud service provider network 110and dedicated to a single cloud subscriber 105, such as an enterprise.Multiple traffic flows can be multiplexed over the cloud subscriberinterface using logical connections.

Across the cloud subscriber interface, cloud subscriber 105 mayestablish a connection (e.g., a cloud virtual connection (VC)) withresources of cloud service provider network 110, such as virtualmachines (VMs) and applications (e.g., VNFs), and/or the like. Cloudsubscriber 105 and cloud service provider network 110 may exchange cloudservice packets across the cloud subscriber interface. A cloud servicepacket may include a Layer 1 (L1) frame, an Ethernet frame, an Internetprotocol (IP) packet, a multiprotocol label switching (MPLS) packet, anapplication protocol data unit (PDU), and/or the like. A cloud servicepacket transmitted across the cloud subscriber interface toward cloudservice provider network 110 may be referred as an ingress cloud servicepacket, and a cloud service packet transmitted across the cloudsubscriber interface toward cloud subscriber 105 may be referred to asan egress cloud service packet.

In some implementations, the cloud subscriber interface may supportLayer 1 (L1 or physical layer), Layer 2 (L2 or data link layer), Layer 3(L3 or network layer), Layer 4 (L4 or transport layer), Layer 5 (L5 orsession layer), Layer 6 (L6 or presentation layer), and Layer 7 (L7 orapplication layer) protocols in the data plane, the control plane,and/or the management plane. Cloud connectivity UNI 125 may support theL1 through L3 protocols in the data plane, the control plane, and/or themanagement plane, and cloud application UNI 130 may support the L2through L7 protocols in the data plane, the control plane, and/or themanagement plane.

Applications and connectivity to the applications may be provided by oneor more connectivity operators 115 and cloud operators 120 that aresubcontracted by the cloud service provider for providing a cloudservice to cloud subscriber 105. For example, a cloud service providercan implement the cloud service for cloud subscriber 105 bysubcontracting with one or more operators. Each operator may provide aconnectivity service (e.g., connectivity operator 115) or a cloudservice (e.g., cloud operator 120). Two connectivity operators 115-A and115-B may interface with each other via a cloud operator-operatorinterface, as shown to the right in FIG. 1C. As shown at the top in FIG.1C, cloud subscriber 105 and cloud service provider 110 may interfacevia cloud connectivity UNI 125. Application UNI can be represented asUNI-S and UNI-P that are separately administered functional componentsof Application UNI. A cloud application UNI-S 130 may be located withincloud subscriber 105, and a cloud application UNI-P 130 may be locatedwithin cloud service provider 110. Cloud connectivity UNI 125 may beprovided at a location where physical connectivity occurs between cloudsubscriber 105 and cloud service provider 110.

The cloud operator-operator interface may include a cloud connectivityexternal network-to-network interface (ENNI) 135 and cloud applicationENNIs 140. Two cloud operators 120-A and 120-B may interface with eachother via a cloud operator-operator interface, as shown to the left inFIG. 1D. The cloud operator-operator interface may include a cloudconnectivity ENNI 135 and cloud application ENNIs 140. Cloudconnectivity operator 115-B and cloud operator 120-A may interface witheach other via a cloud operator-operator interface, as shown to theright in FIG. 1D. The cloud operator-operator interface may include acloud connectivity ENNI 135 and cloud application ENNIs 140.

As shown to the left in FIG. 1E, the cloud operator-operator interfacemay be split between cloud connectivity ENNI 135 and cloud applicationENNI 140. In this way, the cloud operator-operator interface enablesseparate capabilities (e.g., connectivity and applications) to besupported by separate cloud provider entities (e.g., connectivityoperators 115 and cloud operators 120). As shown in the middle in FIG.1E, the cloud operator-operator interface may include only cloudconnectivity ENNI 135, and may omit cloud application ENNI 140, whenonly connectivity services are offered at the cloud operator-operatorinterface. As shown to the right in FIG. 1E, the cloud operator-operatorinterface may include cloud connectivity ENNI 135, and cloud applicationENNI 140 may be located within cloud operator 120-A and within cloudoperator 120-B. Cloud connectivity ENNI 125 of the cloudoperator-operator interface may be provided at a location where physicalconnectivity occurs between cloud operator 120-A and within cloudoperator 120-B. Cloud application ENNI 140 may be provided between cloudoperator 120-A and cloud operator 120-B applications. As shown at thetop in FIG. 1E, the cloud operator-operator interface may include cloudconnectivity ENNI 135, cloud application ENNI-OA 140 may be locatedwithin and administered by cloud operator 120-A, and cloud applicationENNI-OB 140 may be located within and administered by cloud operator120-B. Cloud connectivity ENNI 135 of the cloud operator-operatorinterface may be provided at a location where physical connectivityoccurs between cloud operator 120-A and cloud operator 120-B.

The cloud operator-operator interface may demarcate domains under theresponsibility of each operator 120 for cloud services. In someimplementations, the cloud operator-operator interface may support theL1 through L7 protocols in the data plane, the control plane, and/or themanagement plane. Cloud connectivity ENNI 135 may support the L1 throughL3 protocols in the data plane, the control plane, and/or the managementplane, and cloud application ENNI 140 may support the L2 through L7protocols in the data plane, the control plane, and/or the managementplane.

A cloud application interface (e.g., cloud application UNI-S 130) mayinclude an interface of a cloud service application or a cloud serviceplatform supported by cloud operator 120 or cloud service providernetwork 110. Therefore, the cloud application interface may be aninterface of a VNF, a VM, a container, and/or the like, as shown in FIG.1F. As shown at the top of FIG. 1F, the cloud application interface mayconnect VNFs 145 provided by cloud subscriber 105 with a cloudconnectivity interface (e.g., cloud connectivity UNI 125) via cloudvirtual connection (VC) end points (EPs). The cloud VC EPs may connect,via cloud VCs, with other cloud VC EPs associated with an application P(Provider) or UNI-P 150 provided by cloud service provider network 110.In one example, VNF 145 may be a firewall as part ofsecurity-as-a-service (SECaaS), a software-defined wide area network(SD-WAN) edge as part of a SD-WAN service, and/or the like.

As shown at the bottom of FIG. 1F, the cloud application interface mayconnect a VIVI 155 and a container 160 provided by cloud subscriber 105to the application provided by cloud service provider network 110 via acloud VC with an EP on the application (e.g., with the cloudconnectivity interface via cloud VC EPs). The cloud VC with EPs mayconnect with other cloud VC EPs associated with application P or UNI-P150 provided by cloud service provider network 110. In one example, VIVI155 and container 160 may be a part of a virtualization platformsupporting a platform-as-a-service (PaaS). In some implementations, thecloud application interface may support the L2 through L7 protocols inthe data plane, the control plane, and/or the management plane. Forexample, the cloud application interface may be an L2 interface for WANoptimization, an L3 interface for an SD-WAN and a virtual router, an L7interface for multimedia applications, and/or the like.

FIG. 1G depicts a connection and connection end points providing cloudservices for a cloud VC crossing one or more administrative domains.When a cloud VC crosses multiple cloud operators 120, the cloud VC andcloud VC EPs in each cloud operator 120 may be referred to as anoperator cloud VC and operator cloud VC EPs, respectively. As shown atthe top of FIG. 1G, the cloud VC may be provided between two cloud VCEPs residing on resources of cloud service provider network 110. Asshown at the bottom of FIG. 1G, the cloud VC may be provided between acloud VC EP residing on resources of connectivity operator 115-B andanother cloud VC EP residing on resources of cloud operator 120-A.

The cloud VC EP is a logical end point of a cloud VC, where the cloud VCterminates at application UNI-S 130 to which a particular subset ofcloud service packets that traverse application UNI-S 130 is mapped. Theparticular subset of cloud service packets may be identified via varioustechniques, such as via application identifiers, source IP addresses,destination IP addresses, virtual local area network (VLAN) identifiers(IDs), and/or the like. Properties may be associated with the cloud VCEP, such as an identifier of application UNI-S 130, availability,bandwidth profile, parameters of security functionalities,administrative state, operational state, and/or the like.

The cloud VC may be associated with two or more cloud VC EPs. Forexample, the cloud VC may include an Ethernet VC (EVC), an IP VC, anSD-WAN VC, and/or the like. Properties may be associated with the cloudVC, such as identifiers of cloud VC EPs associated with the cloud VC,connection type, service level specification (SLS), redundancy,connection start time, connection duration, connection period, billingoptions, maximum size of PDUs transmitted over the cloud VC,administrative and operational states, and/or the like.

The cloud VC may cross multiple operator domains (e.g., cloud operators120-A and 120-B), as shown at the top of FIG. 1H. Each of cloudoperators 120-A and 120-B may include a component of the cloud VC,referred to as an operator cloud VC. An operator cloud VC may be anothercloud VC, but may be referred to as an operator cloud VC to identify aconnection, such as a component connection or an end-to-end connection.The operator cloud VC may be a cross connect between two cloud VC EPs,and may be similar to an operator VC of carrier Ethernet services, alink state protocol (LSP), an IP virtual private network (VPN)connection component, an SD-WAN connection, and/or the like. Theproperties of an operator cloud VC may be similar to those for a cloudVC.

Subscriber cloud services may be provided among two or more cloudsubscribers 105, between cloud subscribers 105 and applications P/UNI-P150 provided by cloud service provider network 110, between cloudsubscribers 105 and applications of cloud subscribers 105, and/or thelike. On the other hand, operator cloud services may be provided amongtwo or more cloud operators 120 and connectivity operators 115, amongapplications of cloud operators 120, and/or the like.

As shown at the bottom of FIG. 1H, a cloud VC provided among cloudsubscribers 105 may terminate at cloud subscriber interfaces (e.g.,cloud connectivity UNIs 125). As shown at the top of FIG. 1I, a cloud VCprovided among cloud subscribers 105 may terminate at cloud applicationinterfaces (e.g., cloud application S/UNI-Ss 130). As shown at thebottom of FIG. 1I, a cloud VC provided among cloud subscribers 105 mayterminate at a cloud subscriber interface (e.g., cloud connectivity UNI125) and a cloud application interface (e.g., cloud application S/UNI-S130).

As shown at the top of FIG. 1J, a cloud VC provided among cloudoperators 120 and/or connectivity operators 115 may terminate at cloudoperator interfaces (e.g., cloud connectivity ENNIs 135) or cloudapplication interfaces (e.g., cloud application P/ENNI-OA or ENNI-OB140). As shown at the bottom of FIG. 1J, any one of the cloud operators(e.g., cloud operators 120-A or 120B) may act as a cloud serviceprovider. Remaining cloud operators may provide operator cloud servicesto the cloud operator acting as the cloud service provider. In someimplementations, the cloud operators may jointly establish cloudconnectivity ENNIs 135 from connectivity operator 115 for communicationsvia a cloud VC. The cloud VC provided among cloud operators 120-A and120-B may terminate at cloud application interfaces (e.g., cloudapplication P/ENNI-OA or ENNI-OB 140). For example, connectivityoperator 115 may provide connectivity services (e.g., NaaS) to the cloudoperator acting as the cloud service provider.

In some implementations, cloud subscribers 105 may be concerned about anend-to-end service and not about service implementation, while cloudservice provider network 110 and cloud operators 120 may be concernedabout the service implementation. In some implementations, cloudsubscribers 105 may be interested in self-configuration andself-management of services. The top of FIG. 1K provides a generalrepresentation of subscriber views of cloud services provided by cloudservice provider network 110 to cloud subscriber 105. As shown at thetop of FIG. 1K, a cloud subscriber interface (e.g., cloud connectivityUNI 125) may be provided between cloud subscriber 105 and cloud serviceprovider network 110 in order to connect a cloud service (e.g., cloudapplication S/UNI-S 130) with cloud subscriber 105. The bottom of FIG.1K provides a case where cloud subscriber 105 accesses cloud serviceprovider network 110 via a private network and cloud application S/UNI-S130 is not at a demarcation point as cloud connectivity UNI 125. Theprivate network for connecting to applications may be provided by cloudservice provider network 110. As further shown at the bottom of FIG. 1K,a cloud VC provided between cloud subscriber 105 and cloud serviceprovider network 110 may terminate at cloud application interfaces(e.g., cloud application S/UNI-Ss 130).

The top of FIG. 1L depicts cloud services provided by cloud operator 120to cloud subscriber 105 over a network 165 (e.g., the Internet).Physical connectivity to network 165 may be provided by cloudconnectivity UNIs 120 (e.g., virtual connections, such as VPN overInternet) and may enable applications P 150 associated with cloudoperator 120 to be visible to cloud subscriber 105. Functionalitiesassociated with the connectivity may be distributed over cloudsubscriber 105, network 165, and cloud operator 120 via a cloud VC. Asfurther shown at the top of FIG. 1L, the cloud VC provided between cloudsubscriber 105 and cloud operator 120 may terminate at application S 150provided in cloud subscriber 105 and application P provided in cloudoperator 120. In one example, cloud subscriber 105 may utilize network165 access from a local Internet Service Provider (ISP) to connect toapplication P 150 of cloud operator 120 and may purchase applications150 from cloud operator 120. When there is a problem with network 165access, cloud subscriber 105 may resolve the problem with the ISP andcloud operator 120. When there is a problem with applications P 150,cloud subscriber 105 may resolve the problem with cloud operator 120. Arole of cloud subscriber 105 may not change whether the access to cloudoperator 120 is provided by an ISP or by a private network operator.

As shown at the bottom of FIG. 1L, cloud subscriber 105 may access cloudoperator 120 via connectivity operator 115 that is connected to cloudoperator 120 via a cloud exchange gateway. The cloud exchange gatewaymay provide connectivity among multiple parties, such as connectivityoperator 115 and cloud operator 120. As further shown at the bottom ofFIG. 1L, a cloud VC provided between cloud subscriber 105 and cloudoperator 120 may terminate at application S 150 provided in cloudsubscriber 105 and application P 150 provided in cloud operator 120.

The top of FIG. 1M depicts a cloud service provided to cloud subscriber105 by cloud service provider network 110. Application P 150 may beprovided by cloud operator 120-B, and connectivity to application P 150may be provided by cloud operator 120-A. Cloud service provider network110 may provide coordination between connectivity operator 115 and cloudoperator 120-B. In some implementations, connectivity operator 115,cloud operator 120-B, or a third party may be a cloud service provideracting as a single point of contact for cloud subscriber 105. A cloud VCprovided between cloud subscriber 105 and connectivity operator 115 mayterminate at application UNI-S 130 provided in cloud subscriber 105 andapplications P 150 provided in cloud operator 120-B.

As further shown at the top of FIG. 1M, cloud connectivity ENNI 135provided between connectivity operator 115 and cloud operator 120-B maybe visible to each of connectivity operator 115 and cloud operator120-B. However, the service (e.g., including connectivity and/orapplications) provided by each of connectivity operator 115 and cloudoperator 120-B to cloud service provider network 110 may not be visibleto the other cloud operator unless the other cloud operator is the cloudservice provider. Furthermore, cloud connectivity UNI 125 for cloudsubscriber 105 may be visible to connectivity operator 115.

As further shown at the top of FIG. 1M, connectivity operator 115 mayprovide connectivity for cloud subscriber 105 to cloud operator 120-B asa network-as-a-service (NaaS). Cloud operator 120-B may provideapplication P 150 to cloud service provider network 110 as a cloudservice, such as a software-as-a-service (SaaS), a platform-as-a-service(PaaS), an infrastructure-as-a-service (IaaS), and/or the like. In someimplementations, cloud subscriber 105 may support cloud connectivity UNI125 or both cloud connectivity UNI 125 and cloud application S/UNI-S 130at the cloud subscriber interface, which may be provided between cloudsubscriber 105 and connectivity operator 115.

As shown at the bottom of FIG. 1M, cloud subscriber 105 may act as acloud service provider, and cloud service provider network 110 may beomitted. In some implementations, cloud subscriber 105 may arrangeseparate services with connectivity operator 115 and cloud operator120-B in order to obtain a desired overall service. For example, cloudsubscriber 105 may arrange an NaaS service with connectivity operator115 and may arrange a cloud service with cloud operator 120-B.

FIG. 1N depicts the configuration shown at the top of FIG. 1M. However,the configuration of FIG. 1N includes a local VC that terminates insidecloud subscriber 105 at application S 150.

As shown in FIG. 1O, a cloud service may be provided by connectivityoperator 115 and two cloud operators 120-B and 120-C. Connectivityoperator 115 may connect cloud subscriber 105 to cloud operator 120-B.Cloud operator 120-B and cloud operator 120-C may provide applications P150 and components of a multipoint or a point-to-point cloud VCinitiated by cloud subscriber 105. Such a configuration may supportvarious cloud services.

For example, for a VoIP service, cloud operator 120-B may support asession border controller (SBC) application with a virtual SBC (vSBC)VNF, and cloud operator 120-C may support a firewall (FW) applicationwith a virtual FW (vFW) VNF. vSBC and vFW may execute over themultipoint or point-to-point cloud VC. In this configuration, eachapplication may execute separately. vSBC may be considered acommunications-as-a-service (CaaS) application and vFW may be considereda security-as-a-service (SECaaS) application. Therefore, in thisexample, cloud operator 120-A may provide NaaS and cloud operator 120-Bmay provide CaaS to cloud service provider network 110, and cloudoperator 120-C may provide SECaaS to cloud service provider network 110.An end-to-end cloud service provided by cloud service provider network110 to cloud subscriber 105 may be referred to as a combination of CaaSand SECaaS.

In some implementations, applications P 150 provided by cloud operator120 may be accessed via the Internet. Given that the Internet providesbest-effort service, non-mission critical applications and applicationsthat are less sensitive to network delay, jitter, and/or loss may bemore likely to be accessed via the Internet. In some implementations,cloud subscribers 105 may utilize private networks to access missioncritical applications and applications that are sensitive to networkdelay, jitter, and/or loss, and the Internet may be used as a back-upfor connectivity.

Implementations described herein may be utilized to provide cloudoperator 120 access using the Internet and a private network. Forexample, an employee (e.g., cloud subscriber 105) of an enterprise mayutilize an enterprise network (e.g., a private network) to access cloudoperator 120 or may utilize the Internet to directly access cloudoperator 120. An interface between the enterprise network and cloudoperator 120 may include stricter security capabilities compared to aninterface between the Internet and cloud operator 120. In such anexample, a branch office of the enterprise, with no access to theenterprise network, may access a virtual router provided by cloudoperator 120 via the Internet. Cloud operator 120 may include a gatewayto the enterprise network that provides connectivity to the branchoffice. In some implementations, cloud subscribers 105 may accessapplications P 150 hosted by multiple cloud operators 120 via theInternet or via a private network.

Applications P 150 and connectivity to applications P 150 can beprovided by a single cloud operator 120 (e.g., a telecommunicationsservice provider). A private network of cloud operator 120 may includean L1 network, an L2 network, an L3 network, a wireless network, anSD-WAN, and/or the like. In some implementations, connectivity andapplications P 150 may be provided by two different cloud operators 120.

In some implementations, cloud operator 120-A may team up with cloudoperator 120-B and offer applications P 150 to cloud subscribers 105over a private network. Cloud subscribers 105 may only interact with oneof cloud operators 120-A and 120-B and may be unaware of the locationsof applications P 150. One of cloud operators 120-A and 120-B may managethe private network and may play a role of connectivity operator 115.

In some implementations, establishing a cloud operator interface betweentwo connectivity operators 115, between connectivity operator 115 andcloud operator 120, or between two cloud operators 120 may not always beeconomically justified. In such cases, a cloud exchange network device(e.g., a gateway) may provide connectivity among such entities. Via thecloud exchange network device, cloud subscribers 105 may be able to movevirtualized components (e.g. applications P 150, VNFs, VMs, containers,and/or the like) from one cloud operator 120 to another. Cloudsubscribers 105 may place the virtualized components in multiple cloudoperators 120 and may establish service function chaining among them.

Implementations described herein may be utilized to provide one or morecloud services. A cloud service may include an end-to-end service withone or more of platform components, such as compute and storage,applications, and connectivity among the aforementioned, that may beaccessed by cloud subscriber 105 from one or more locations. A cloudservice may include an end-to-end service among cloud subscribers 105,connectivity operators 115, and cloud operators 120 that providesvirtual and non-virtual resources. The cloud services may be grouped ina network-as-a-service (NaaS), an infrastructure-as-a-service (IaaS), aplatform-as-a-service (PaaS), a software-as-a-service (SaaS), acommunications-as-a-service (CaaS), a security-as-a-service (SECaaS),and/or the like categories. Cloud services in a same category mayinclude similar characteristics.

NaaS may deliver assured and dynamic connectivity services via a virtualconnection, and via virtual, or both physical and virtual, serviceendpoints over one or more operator networks. Such services may enableusers, applications, and/or systems to create, modify, suspend/resume,and/or terminate connectivity services through standardized applicationprogramming interfaces (APIs). Such services may be assured from bothperformance and security perspectives. NaaS may support connectivitythrough homogenous or heterogeneous networks by one or more cloudoperators 120, where one of cloud operators 120 may act as a cloudservice provider; may provide on-demand network configurationcapability; may guarantee quality of service (QoS) according to thenegotiated service level specifications; and/or may provide connectionsecurity that includes encryption. An NaaS provider (e.g., connectivityoperator 115 or cloud service provider network 110) may maintain andmanage network resources. In some implementations, cloud serviceprovider network 110 may not own the NaaS, but may provide coordinationwith connectivity operator 115 for the NaaS.

An IaaS may provision processing, storage, networks, and otherfundamental computing resources for cloud subscriber 105 so that cloudsubscriber 105 may deploy and execute arbitrary software (e.g.,operating systems and applications). Cloud subscriber 105 might notmanage or control an underlying cloud infrastructure, but may havecontrol over operating systems, storage, deployed applications, andpossibly limited control over select networking components (e.g., hostfirewalls).

A PaaS may enable cloud subscriber 105 to deploy, onto a cloudinfrastructure, subscriber-created or acquired applications P 150created using programming languages and tools supported by cloudoperator 120. Cloud subscriber 105 might not manage or control theunderlying cloud infrastructure (e.g., a network, servers, operatingsystems, storage, and/or the like), but may control deployedapplications and possibly an application hosting environment. A PaaS mayinclude a standalone development environment that does not includetechnical, licensing, and/or financial dependencies on specific SaaSapplications or web services. A PaaS may include an applicationdelivery-only environment that does not include development, debugging,and/or test capabilities as part of the service. A PaaS may be an openplatform-as-a-service that does not include hosting, but rather providesopen source software to allow a PaaS provider to execute applications.Some open platforms with an external API may enable a developer to useany programming language, database, operating system, server, and/or thelike to deploy applications. With PaaS, a scalable and high-performingnetwork may be formed with a fully-managed application platform forexecuting and consolidating software applications and databases. A PaaSmay be provided via a data center, a cloud-in-a-box, and/or the like.The cloud-in-a-box may be deployed at a customer premises provided bycloud service provider network 110. A VNF owned and maintained by cloudsubscriber 105 may execute over the cloud-in-a-box to perform a servicefunction, such as security. The VNF may perform service functionchaining with another VNF provided by cloud operator 120 in order tosupport additional capabilities.

An SaaS may enable cloud subscriber 105 to utilize applications P 150provided by cloud operator 120 and executing on a cloud infrastructure.Applications P 150 may be accessible to cloud subscriber 105 via a thinclient interface (e.g., a web browser, web-based email, and/or thelike). Cloud subscriber 105 might not manage or control the underlyingcloud infrastructure, such as a network, servers, operating systems,storage, application capabilities, and/or the like.

A CaaS may provide real-time services, such as a virtual private branchexchange (PBX), voice and video conferencing systems, collaborationsystems, call centers, local and domestic long distance point-to-pointor multipoint voice calling, fixed mobile convergence (e.g., acombination of fixed broadband and local access wireless technologies),voicemail, integrated business communications, point-to-point ormultipoint video calling, point-to-point or multipoint videoconferencing, professional voice recording services, and/or the like.

In this way, several different stages of the process for supportingseparate cloud services may be enhanced with a cloud computingenvironment that includes split connectivity and application interfaces,which may improve speed and efficiency of the process and conservecomputing resources (e.g., processing resources, memory resources,communication resources, and/or the like), networking resources, and/orthe like. Furthermore, implementations described herein use a rigorous,computerized process to perform tasks or roles that were not previouslyperformed. For example, currently there does not exist a technique thatsupports separate cloud services with a cloud computing environment thatincludes split connectivity and application interfaces. Finally, theprocess for supporting separate cloud services conserves computingresources (e.g., processing resources, memory resources, communicationresources, and/or the like), networking resources, and/or the like thatwould otherwise be wasted attempting to provide the cloud serviceswithout the split connectivity and application interfaces.

As indicated above, FIGS. 1A-1O are provided merely as examples. Otherexamples may differ from what is described with regard to FIGS. 1A-1O.The number and arrangement of devices and networks shown in FIGS. 1A-1Oare provided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 1A-1O. Furthermore, two or more devices shown in FIGS.1A-1O may be implemented within a single device, or a single deviceshown in FIGS. 1A-1O may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) of FIGS. 1A-1O may perform one or more functions describedas being performed by another set of devices of FIGS. 1A-1O.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,environment 200 may include cloud subscriber 105, cloud service providernetwork 110, and network 165. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Cloud subscriber 105 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, cloud subscriber 105 mayinclude a mobile phone (e.g., a smart phone, a radiotelephone, and/orthe like), a laptop computer, a tablet computer, a desktop computer, ahandheld computer, a gaming device, a wearable communication device(e.g., a smart watch, a pair of smart glasses, a heart rate monitor, afitness tracker, smart clothing, smart jewelry, a head mounted display,and/or the like), or a similar type of device. In some implementations,cloud subscriber 105 may receive information from and/or transmitinformation to cloud service provider network 110.

Cloud service provider network 110 includes one or more devices thatsupport separate cloud services with a cloud computing environment thatincludes split connectivity and application interfaces. In someimplementations, cloud service provider network 110 may be designed tobe modular such that certain software components may be swapped in orout depending on a particular need. As such, cloud service providernetwork 110 may be easily and/or quickly reconfigured for differentuses. In some implementations, cloud service provider network 110 mayreceive information from and/or transmit information to one or morecloud subscribers 105.

In some implementations, as shown, cloud service provider network 110may be hosted in a cloud computing environment 210. Notably, whileimplementations described herein describe cloud service provider network110 as being hosted in cloud computing environment 210, in someimplementations, cloud service provider network 110 may not becloud-based (i.e., may be implemented outside of a cloud computingenvironment) or may be partially cloud-based.

Cloud computing environment 210 includes an environment that hosts cloudservice provider network 110. Cloud computing environment 210 mayprovide computation, software, data access, storage, etc., services thatdo not require end-user knowledge of a physical location andconfiguration of system(s) and/or device(s) that hosts cloud serviceprovider network 110. As shown, cloud computing environment 210 mayinclude a group of computing resources 220 (referred to collectively as“computing resources 220” and individually as “computing resource 220”).

Computing resource 220 includes one or more personal computers,workstation computers, mainframe devices, or other types of computationand/or communication devices. In some implementations, computingresource 220 may host cloud service provider network 110. The cloudresources may include compute instances executing in computing resource220, storage devices provided in computing resource 220, data transferdevices provided by computing resource 220, etc. In someimplementations, computing resource 220 may communicate with othercomputing resources 220 via wired connections, wireless connections, ora combination of wired and wireless connections. In someimplementations, one or more computing resources 220 may correspond toone or more connectivity operators 115, one or more cloud operators 120,and/or the like. For example, connectivity operator 115 and/or cloudoperator 120 may provide the functionalities described herein via one ormore computing resources 220.

As further shown in FIG. 2, computing resource 220 includes a group ofcloud resources, such as one or more applications (“APPs”) 220-1, one ormore virtual machines (“VMs”) 220-2, virtualized storage (“VSs”) 220-3,one or more hypervisors (“HYPs”) 220-4, and/or the like.

Application 220-1 includes one or more software applications that may beprovided to or accessed by client devices associated with cloudcomputing environment 210. Application 220-1 may eliminate a need toinstall and execute the software applications on client devices. Forexample, application 220-1 may include software associated with cloudservice provider network 110 and/or any other software capable of beingprovided via cloud computing environment 210. In some implementations,one application 220-1 may send/receive information to/from one or moreother applications 220-1, via virtual machine 220-2.

Virtual machine 220-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine, andmay include a one or more containers. Virtual machine 220-2 may beeither a system virtual machine or a process virtual machine, dependingupon use and degree of correspondence to any real machine by virtualmachine 220-2. A system virtual machine may provide a complete systemplatform that supports execution of a complete operating system (“OS”).A process virtual machine may execute a single program and may support asingle process. In some implementations, virtual machine 220-2 mayexecute on behalf of a user (e.g., a user of a client device or anoperator of cloud service provider network 110), and may manageinfrastructure of cloud computing environment 210, such as datamanagement, synchronization, or long-duration data transfers.

Virtualized storage 220-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 220. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 220-4 may provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as computing resource 220.Hypervisor 220-4 may present a virtual operating platform to the guestoperating systems and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Network 165 includes one or more wired and/or wireless networks. Forexample, network 165 may include a cellular network (e.g., a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the Public Switched Telephone Network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, and/or the like, and/or a combination of these orother types of networks.

In some implementations, network 165 may include one or more networkdevices. A network device includes one or more devices (e.g., one ormore traffic transfer devices) capable of receiving, providing, storing,generating, and/or processing information described herein. For example,the network device may include a firewall, a router, a policy enforcer,a gateway, a switch, a hub, a bridge, a reverse proxy, a server (e.g., aproxy server), a security device, an intrusion detection device, a loadbalancer, or a similar device. In some implementations, the networkdevice may receive information from and/or provide information to one ormore other devices of environment 200. In some implementations, thenetwork device may be a physical device implemented within a housing,such as a chassis. In some implementations, the network device may be avirtual device implemented by one or more computer devices of a cloudcomputing environment or a data center.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to cloud subscriber 105, cloud service provider network110, and/or computing resource 220. In some implementations, cloudsubscriber 105, cloud service provider network 110, and/or computingresource 220 may include one or more devices 300 and/or one or morecomponents of device 300. As shown in FIG. 3, device 300 may include abus 310, a processor 320, a memory 330, a storage component 340, aninput component 350, an output component 360, and a communicationinterface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid-state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for supporting separatecloud services with a cloud computing environment that includes splitconnectivity and application interfaces. In some implementations, one ormore process blocks of FIG. 4 may be performed by a cloud serviceprovider network (e.g., cloud service provider network 110). In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including thecloud service provider network, such as a cloud subscriber (e.g., cloudsubscriber 105), a connectivity operator (e.g., connectivity operator115), and/or a cloud operator (e.g., cloud operator 120).

As shown in FIG. 4, process 400 may include receiving, from a cloudsubscriber device, a request to access an application, wherein the cloudservice provider network includes a split interface associated with thecloud subscriber device, and wherein the split interface includes aconnectivity interface associated with a connectivity operator deviceand an application interface associated with a cloud operator device(block 410). For example, the cloud service provider network (e.g.,using computing resource 220, processor 320, communication interface370, and/or the like) may receive, from a cloud subscriber device, arequest to access an application, as described above. In someimplementations, the cloud service provider network may include a splitinterface associated with the cloud subscriber device. In someimplementations, the split interface may include a connectivityinterface associated with a connectivity operator device, and anapplication interface associated with a cloud operator device.

As further shown in FIG. 4, process 400 may include providing, to thecloud operator device, the request to access the application, whereinthe cloud operator device stores the application (block 420). Forexample, the cloud service provider network (e.g., using computingresource 220, processor 320, memory 330, communication interface 370,and/or the like) may provide, to the cloud operator device, the requestto access the application, as described above. In some implementations,the cloud operator device may store the application.

As further shown in FIG. 4, process 400 may include receiving, from thecloud operator device, the application, based on the request to accessthe application (block 430). For example, the cloud service providernetwork (e.g., using computing resource 220, processor 320, storagecomponent 340, communication interface 370, and/or the like) mayreceive, from the cloud operator device, the application, based on therequest to access the application, as described above.

As further shown in FIG. 4, process 400 may include providing theapplication to the cloud subscriber device via the application interfaceof the split interface, wherein the connectivity interface connects thecloud subscriber device and the cloud operator device so that theapplication is provided to the cloud subscriber device via theapplication interface (block 440). For example, the cloud serviceprovider network (e.g., using computing resource 220, processor 320,output component 360, communication interface 370, and/or the like) mayprovide the application to the cloud subscriber device via theapplication interface of the split interface, as described above. Insome implementations, the connectivity interface may connect the cloudsubscriber device and the cloud operator device so that the applicationis provided to the cloud subscriber device via the applicationinterface.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the connectivity interface may support aphysical layer protocol, a data link layer protocol, and a network layerprotocol in a data plane, a control plane, and a management plane; andthe application interface may support the data link layer protocol, thenetwork layer protocol, a transport layer protocol, a session layerprotocol, a presentation layer protocol, and an application layerprotocol in the data plane, the control plane, and the management plane.

In a second implementation, alone or in combination with the firstimplementation, the connectivity interface may include one of auser-to-network interface (UNI) or an external network-to-networkinterface (ENNI), and the application interface may include one of theUNI or the ENNI.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the cloud service provider networkmay cause a cloud service to be provided to the cloud subscriber device.In some implementations, the cloud service may be provided by anothercloud operator device.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the cloud service may includeone or more of network-as-a-service, infrastructure-as-a-service,platform-as-a-service, software-as-a-service,communications-as-a-service, or security-as-a-service.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the other cloud operatordevice may communicate with the cloud operator device via another splitinterface that includes another connectivity interface and anotherapplication interface.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, the application interface mayconnect a virtual network function, a virtual machine, and/or acontainer, provided by the cloud subscriber device, with the applicationvia a cloud virtual connection.

In a seventh implementation, alone or in combination with one or more ofthe first through sixth implementations, the cloud subscriber device mayaccess the cloud service provider network via a private network and theconnectivity interface.

In an eighth implementation, alone or in combination with one or more ofthe first through sixth implementations, the cloud subscriber device mayaccess the cloud service provider network via a public network and theconnectivity interface.

In a ninth implementation, alone or in combination with one or more ofthe first through eighth implementations, the connectivity operatordevice may connect with the cloud operator device and may enableconnectivity of the cloud subscriber device to the cloud operatordevice.

In a tenth implementation, alone or in combination with one or more ofthe first through ninth implementations, the split interface may includea bi-directional link that provides traffic, control plane, andmanagement capabilities required by the cloud service provider networkand dedicated to the cloud subscriber device.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, and/or the like), and may be used interchangeably with“one or more.” Where only one item is intended, the phrase “only one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

1. A method, comprising: receiving, by a device and from a cloudsubscriber device, a request to access an application, wherein thedevice includes a split interface associated with the cloud subscriberdevice, wherein the split interface includes: a connectivity interfaceassociated with a connectivity operator device, and an applicationinterface associated with a cloud operator device,  wherein theapplication interface is operated by the cloud subscriber device;providing, by the device and to the cloud operator device, the requestto access the application, wherein the cloud operator device stores theapplication; receiving, by the device and from the cloud operatordevice, the application based on the request to access the application;and providing, by the device, the application to the cloud subscriberdevice via the application interface of the split interface, wherein:the connectivity interface connects the cloud subscriber device and thecloud operator device, and the application tunnels through to the cloudsubscriber device via the application interface.
 2. The method of claim1, wherein: the connectivity interface supports a physical layerprotocol, a data link layer protocol, and a network layer protocol in adata plane, a control plane, and a management plane; and the applicationinterface supports the data link layer protocol, the network layerprotocol, a transport layer protocol, a session layer protocol, apresentation layer protocol, and an application layer protocol in thedata plane, the control plane, and the management plane.
 3. The methodof claim 1, wherein: the connectivity interface includes one of auser-to-network interface (UNI) or an external network-to-networkinterface (ENNI); and the application interface includes one of the UNIor the ENNI.
 4. The method of claim 1, further comprising: causing acloud service to be provided to the cloud subscriber device, wherein thecloud service is provided by another cloud operator device.
 5. Themethod of claim 4, wherein the cloud service includes one or more of:network-as-a-service, infrastructure-as-a-service, aplatform-as-a-service, software-as-a-service,communications-as-a-service, or security-as-a-service.
 6. The method ofclaim 4, wherein the other cloud operator device communicates with thecloud operator device via another split interface that includes: anotherconnectivity interface, and another application interface.
 7. The methodof claim 1, wherein the application interface connects a virtual networkfunction, provided by the cloud subscriber device, with the applicationvia a cloud virtual connection.
 8. A device, comprising: one or morememories; and one or more processors, communicatively coupled to the oneor more memories, configured to: receive, from a cloud subscriberdevice, a request to access an application, wherein the device includesa split interface associated with the cloud subscriber device, whereinthe split interface includes:  a connectivity interface associated witha connectivity operator device, and  an application interface associatedwith a cloud operator device,  wherein the connectivity interfaceincludes one of a user-to-network interface (UNI) or an externalnetwork-to-network interface (ENNI),  wherein the application interfaceincludes one of the UNI or the ENNI, and  wherein the applicationinterface is operated by the cloud subscriber device; provide, to thecloud operator device, the request to access the application, whereinthe cloud operator device stores the application; receive, from thecloud operator device, the application based on the request to accessthe application; and provide the application to the cloud subscriberdevice via the application interface of the split interface, wherein:the connectivity interface connects the cloud subscriber device and thecloud operator device, and the application tunnels through to the cloudsubscriber device via the application interface.
 9. The device of claim8, wherein the application interface connects a virtual machine,provided by the cloud subscriber device, with the application via acloud virtual connection.
 10. The device of claim 8, wherein theapplication interface connects a container, provided by the cloudsubscriber device, with the application via a cloud virtual connection.11. The device of claim 8, wherein the cloud subscriber device accessesthe device via a private network and the connectivity interface.
 12. Thedevice of claim 8, wherein the cloud subscriber device accesses thedevice via a public network and the connectivity interface.
 13. Thedevice of claim 8, wherein the connectivity operator device connectswith the cloud operator device and enables connectivity of the cloudsubscriber device to the cloud operator device.
 14. The device of claim8, wherein the split interface includes a bi-directional link thatprovides traffic, control plane, and management capabilities required bythe device and dedicated to the cloud subscriber device.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the one or more processors to:receive, from a cloud subscriber device, a request to access anapplication, wherein the device includes a split interface associatedwith the cloud subscriber device, wherein the split interface includes: a connectivity interface associated with a connectivity operatordevice, and  an application interface associated with a cloud operatordevice,  wherein the application interface is operated by the cloudsubscriber device; provide, to the cloud operator device, the request toaccess the application, wherein the cloud operator device stores theapplication; receive, from the cloud operator device, the applicationbased on the request to access the application; provide the applicationto the cloud subscriber device via the application interface of thesplit interface, wherein: the connectivity interface connects the cloudsubscriber device and the cloud operator device, and the applicationtunnels through to the cloud subscriber device via the applicationinterface; and cause a cloud service to be provided to the cloudsubscriber device, wherein the cloud service is provided by anothercloud operator device.
 16. The non-transitory computer-readable mediumof claim 15, wherein: the connectivity interface supports a physicallayer protocol, a data link layer protocol, and a network layer protocolin a data plane, a control plane, and a management plane; and theapplication interface supports the data link layer protocol, the networklayer protocol, a transport layer protocol, a session layer protocol, apresentation layer protocol, and an application layer protocol in thedata plane, the control plane, and the management plane.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the cloudservice includes one or more of: network-as-a-service,infrastructure-as-a-service, a platform-as-a-service,software-as-a-service, communications-as-a-service, orsecurity-as-a-service.
 18. The non-transitory computer-readable mediumof claim 15, wherein the other cloud operator device communicates withthe cloud operator device via another split interface that includes:another connectivity interface, and another application interface. 19.The non-transitory computer-readable medium of claim 15, wherein theapplication interface connects one or more of a virtual networkfunction, a virtual machine, or a container, provided by the cloudsubscriber device, with the application via a cloud virtual connection.20. The non-transitory computer-readable medium of claim 15, wherein thesplit interface includes a bi-directional link that provides traffic,control plane, and management capabilities required by the device anddedicated to the cloud subscriber device.